Date: Tue, 1 Nov 94 04:30:32 PST From: Ham-Digital Mailing List and Newsgroup Errors-To: Ham-Digital-Errors@UCSD.Edu Reply-To: Ham-Digital@UCSD.Edu Precedence: List Subject: Ham-Digital Digest V94 #360 To: Ham-Digital Ham-Digital Digest Tue, 1 Nov 94 Volume 94 : Issue 360 Today's Topics: 9600bps modem design Is Anyone Responsible (Bad Language in Text) (3 msgs) Mild disappointment in latest Kam+ 7.1 firmware NoCal OO goes after Packet BULLetins (3 msgs) RF into KAMPlus TPK-182 Send Replies or notes for publication to: Send subscription requests to: Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Ham-Digital Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/ham-digital". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: 31 Oct 1994 13:39:00 GMT From: merlin@beta.hut.fi (Jouni Meril{inen) Subject: 9600bps modem design I am considering designing and building a 9600bps modem. It should be compatible with the 9600bps modems currently used in ham packet. Can someone please tell me... - Where can I find the specs? All I know at the moment is it's FSK done in some interesting way. - Are there some schematics available somewhere so I could compare my design others'? ad[thanks]vance -- mail Jouni.Merilainen@hut.fi phone work +358 0 70019923 finger merlin@beta.hut.fi www http://www.hut.fi/~merlin/ ------------------------------ Date: Fri, 28 Oct 1994 23:19:05 GMT From: no8m@hamnet.wariat.org (Steve Wolf NO8M) Subject: Is Anyone Responsible (Bad Language in Text) A bulletin received at NO8M with lots of bad language has been appended. I have two questions. 1. Who is responsible? The originator and first forwarder are located outside the county and not subject to FCC rules. F6FNB, located portable in Texas, is the first United States station to receive the bulletin. He is neither the originator or first forwarder. Trying to then interpret a rule to assign responsibility to him when the meaning of "AUTHOR" and "FIRST FORWARDER" is plain is silly. Hmmmm. No one has any responsibility? 2. Why wasn't it held? This was held based on the bad words matching the MSYS hold file here. Is there not a way with the software used by the other 22 DX and 13 US stations who were involved to hold this at any of them? Do we have 35 BBS stations that can't set up a simple file to hold bad words or is this impossible with them all? Lazy? 73, Steve Sorry about the language. Internet : no8m@hamnet.wariat.org Amateur Radio : no8m@no8m.#neoh.oh.usa.na MSYS Mail List: msys-request@hamnet.wariat.org (info for the subject) S DXNEWS @ WW < DL5UH $ 18A4DB0RBS82 DX-cluster? R:941021/1313z 54991@NO8M.#NEOH.OH.USA.NA $:18A4DB0RBS82 R:941021/0722z 3106@N8KJT.#NEOH.OH.USA.NA $:18A4DB0RBS82 R:941021/0539Z @:KD4AHQ.#AGS.GA.USA.NOAM [TEL-LINK] #:51077 $:18A4DB0RBS82 R:941020/1534Z @:N4QWL.#COL.SC.USA.NOAM [TEL-LINK] $:18A4DB0RBS82 FBB5.15 R:941020/2316Z @:WA7NTF.#TAC.#WWA.WA.USA.NOAM #:27219 [STEILACOOM] R:941020/2254Z @:KB7CNN.#WWA.WA.USA.NOAM #:43506 [N.W.GATEWAY] $:18A4DB0RBS82 R:941020/2205 10805@WA7SJN.#WWA.WA.USA.NOAM B:18A4DB0RBS82 R:941020/2039 57769@N6IYA.#NOCAL.CA.USA.NOAM B:18A4DB0RBS82 R:941020/2025Z @:W6PW.#NOCAL.CA.USA.NOAM #:46357 $:18A4DB0RBS82 R:941020/2019Z @:KA6EYH.#NOCAL.CA.USA.NOAM #:1726 [Daly City] $:18A4DB0RBS82 R:941020/1956Z @:KA6EYH.#NOCAL.CA.USA.NOAM #:60272 [Pacifica] $:18A4DB0RBS82 R:941020/1956Z @:WB0TAX.#NOCAL.CA.USA.NOAM #:1779 $:18A4DB0RBS82 R:941020/1948Z @:N5UXT.LA.USA.NA #:28461 [New Orleans] $:18A4DB0RBS82 R:941020/1936Z @:F6CNB.#SETX.TX.USA.NOAM #:23345 [SugarLand] $:18A4DB0RBS82 R:941020/1904Z @:OH6RBV.#VAA.FIN.EU #:52103 [Vaasa] FBB5.15c $:18A4DB0RBS82 R:941020/1848Z @:OH6RBG.FIN.EU #:5297 [Jakobstad] FBB5.15c $:18A4DB0RBS82 R:941020/1820Z @:SK2AT.AC.SWE.EU #:27831 [Umea] FBB5.15c $:18A4DB0RBS82 R:941020/1810Z @:SM2IRZ.AC.SWE.EU #:56991 [UMEA] FBB5.15c $:18A4DB0RBS82 R:941019/0249Z @:I6BNW.#MC.IMAR.ITA.EU #:6074 [RECANATI] FBB5.15c R:941019/0224Z @:IK6RUY.IMAR.ITA.EU #:39934 [Pergola] FBB5.15c $:18A4DB0RBS82 R:941019/0118Z @:IW3GS.IVEN.ITA.EU #:41444 [Padova] FBB5.15c $:18A4DB0RBS82 R:941019/0117Z @:IW3QQV.IFVG.ITA.EU #:16476 [Palazzolo (Ud) JN65MT] FBB5.15c R:941019/0107Z @:IV3CJT.IFVG.ITA.EU #:14545 [Trieste] FBB5.15c $:18A4DB0RBS82 R:941019/0054Z @:S50BBS.KP.SVN.EU #:10679 [Koper] FBB5.15c $:18A4DB0RBS82 R:941019/0021z @S50BOX S50BOX.SVN.EU Ljubljana Slovenija R:941019/0107l @OE6XYG.AUT.EU [Austria-Net,JN77RA,TheBox 1.9b SYSOP:OE6UBG] R:941019/0001z @:OE3XBS.AUT.EU R:941018/2243z @:DB0LNA.#BAY.DEU.EU R:941018/2254z @:DB0RGB.#BAY.DEU.EU R:941018/2243z @:DB0ABH.#BAY.DEU.EU R:941018/2244z @DB0BOX.#BAY.DEU.EU [DieBox in Nuernberg, JN59NJ, SYSOP: DC3YC] R:941018/2145z @:DB0MRW.#BAY.DEU.EU R:941018/2244z @:DB0SON.#THR.DEU.EU R:941018/2238z @:DB0SIF.#HES.DEU.EU R:941018/2236z @DK0MTV.#RPL.DEU.EU [PKT-Mbox/AMT-Gway, JN49CX, OP: DJ8CY] R:941018/2230z @:DB0RBS.#BW.DEU.EU [SCHWIEBERDINGEN OP:DL1SEM] BCM1.34 From: DL5UH @ DB0RBS.#BW.DEU.EU To : DX @ WW IS THIS REALLY NECCESCARY? DB0SDX 17-Oct-1994 2215Z H oder ? fuer Hilfe eingeben > DX de PE1OSJ: 7069.0 PA0KLS KLAAS FUCKS YOU FOR FREE!! 2222Z DX de PA3FYW: 14100.0 PA0KLS please kill my father. 2223Z DX de PE1OSJ: 50069.0 PA0KLS KLAAS FUCKS YOU FOR FREE!! 2224Z DX de PA3FYW: 50106.0 PA0KLS help me,my father is a devil. 2226Z DX de PE1OSJ: 14169.0 PA0KLS MY FATHER RAPES ME ! 2228Z DX de PE1OSJ: 144269.0 PA3FYW PA0KLS MOTHERFUCKER !!!!! 2231Z DX de PE1OSJ: 432269.0 PA3FYW PA0KLS MOTHERFUCKER !!!!! 2236Z DX de PE1OSJ: 14056.0 PA0KLS FUCK YOURSELF KLAAS !!! 2244Z DX de PE1OSJ: 28450.0 PA0KLS I WILL GET YOU KLAAS !!! 2245Z DX de PI5EHV: 50110.0 PA3FYW PA0KLS CHILDFUCKER 2246Z DX de PA0KLS: 28450.0 PE1OSJ verdammte arschloch ! 2246Z DX de PA0KLS: 14130.0 PA3FYW is my ugly bad son ! 2248Z DX de PE1OSJ: 14250.0 PA0KLS WIE LACHT HET LAATST,klaasje? 2248Z DX de PI5EHV: 144310.0 PE1OSJ PA0KLS,i want YOU 2249Z Eingestellte Parameter PA3FYW: (siehe HELP ALTER) Heimat-MYBBS...(A F).?PI8ZAA.#NBO.NLD.EU Name...........(A N). Letzter Login........Noch nie eingeloggt. Logins 0, Mails erhalten 0, gelesen 0, gesendet 1 Eingestellte Parameter PI5EHV: (siehe HELP ALTER) Heimat-MYBBS...(A F).@PI8ZAA (13.12.93 14:55) Name...........(A N). Letzter Login........Noch nie eingeloggt. Logins 0, Mails erhalten 0, gelesen 0, gesendet 3 /EX -- --- 73, Steve ------------------------------ Date: 31 Oct 1994 13:24:37 -0500 From: k8unp@bcfreenet.seflin.lib.fl.us (Peter Rimmel) Subject: Is Anyone Responsible (Bad Language in Text) Give us all a break and quit hunting witches... Halloween is over and so is the delivery of this "message" Steve Wolf NO8M (no8m@hamnet.wariat.org) wrote: : A bulletin received at NO8M with lots of bad language has been : appended. I have two questions. : 1. Who is responsible? : The originator and first forwarder are located outside the county and not : subject to FCC rules. F6FNB, located portable in Texas, is the first United : States station to receive the bulletin. He is neither the originator or first : forwarder. Trying to then interpret a rule to assign responsibility to him : when the meaning of "AUTHOR" and "FIRST FORWARDER" is plain is silly. : Hmmmm. No one has any responsibility? : 2. Why wasn't it held? : This was held based on the bad words matching the MSYS hold file here. Is : there not a way with the software used by the other 22 DX and 13 US : stations who were involved to hold this at any of them? Do we have 35 : BBS stations that can't set up a simple file to hold bad words or is this : impossible with them all? Lazy? : 73, : Steve : Sorry about the language. : Internet : no8m@hamnet.wariat.org : Amateur Radio : no8m@no8m.#neoh.oh.usa.na : MSYS Mail List: msys-request@hamnet.wariat.org (info for the subject) : S DXNEWS @ WW < DL5UH $ 18A4DB0RBS82 : DX-cluster? : R:941021/1313z 54991@NO8M.#NEOH.OH.USA.NA $:18A4DB0RBS82 : R:941021/0722z 3106@N8KJT.#NEOH.OH.USA.NA $:18A4DB0RBS82 : R:941021/0539Z @:KD4AHQ.#AGS.GA.USA.NOAM [TEL-LINK] #:51077 $:18A4DB0RBS82 : R:941020/1534Z @:N4QWL.#COL.SC.USA.NOAM [TEL-LINK] $:18A4DB0RBS82 FBB5.15 : R:941020/2316Z @:WA7NTF.#TAC.#WWA.WA.USA.NOAM #:27219 [STEILACOOM] : R:941020/2254Z @:KB7CNN.#WWA.WA.USA.NOAM #:43506 [N.W.GATEWAY] $:18A4DB0RBS82 : R:941020/2205 10805@WA7SJN.#WWA.WA.USA.NOAM B:18A4DB0RBS82 : R:941020/2039 57769@N6IYA.#NOCAL.CA.USA.NOAM B:18A4DB0RBS82 : R:941020/2025Z @:W6PW.#NOCAL.CA.USA.NOAM #:46357 $:18A4DB0RBS82 : R:941020/2019Z @:KA6EYH.#NOCAL.CA.USA.NOAM #:1726 [Daly City] $:18A4DB0RBS82 : R:941020/1956Z @:KA6EYH.#NOCAL.CA.USA.NOAM #:60272 [Pacifica] $:18A4DB0RBS82 : R:941020/1956Z @:WB0TAX.#NOCAL.CA.USA.NOAM #:1779 $:18A4DB0RBS82 : R:941020/1948Z @:N5UXT.LA.USA.NA #:28461 [New Orleans] $:18A4DB0RBS82 : R:941020/1936Z @:F6CNB.#SETX.TX.USA.NOAM #:23345 [SugarLand] $:18A4DB0RBS82 : R:941020/1904Z @:OH6RBV.#VAA.FIN.EU #:52103 [Vaasa] FBB5.15c $:18A4DB0RBS82 : R:941020/1848Z @:OH6RBG.FIN.EU #:5297 [Jakobstad] FBB5.15c $:18A4DB0RBS82 : R:941020/1820Z @:SK2AT.AC.SWE.EU #:27831 [Umea] FBB5.15c $:18A4DB0RBS82 : R:941020/1810Z @:SM2IRZ.AC.SWE.EU #:56991 [UMEA] FBB5.15c $:18A4DB0RBS82 : R:941019/0249Z @:I6BNW.#MC.IMAR.ITA.EU #:6074 [RECANATI] FBB5.15c : R:941019/0224Z @:IK6RUY.IMAR.ITA.EU #:39934 [Pergola] FBB5.15c $:18A4DB0RBS82 : R:941019/0118Z @:IW3GS.IVEN.ITA.EU #:41444 [Padova] FBB5.15c $:18A4DB0RBS82 : R:941019/0117Z @:IW3QQV.IFVG.ITA.EU #:16476 [Palazzolo (Ud) JN65MT] FBB5.15c : R:941019/0107Z @:IV3CJT.IFVG.ITA.EU #:14545 [Trieste] FBB5.15c $:18A4DB0RBS82 : R:941019/0054Z @:S50BBS.KP.SVN.EU #:10679 [Koper] FBB5.15c $:18A4DB0RBS82 : R:941019/0021z @S50BOX S50BOX.SVN.EU Ljubljana Slovenija : R:941019/0107l @OE6XYG.AUT.EU [Austria-Net,JN77RA,TheBox 1.9b SYSOP:OE6UBG] : R:941019/0001z @:OE3XBS.AUT.EU : R:941018/2243z @:DB0LNA.#BAY.DEU.EU : R:941018/2254z @:DB0RGB.#BAY.DEU.EU : R:941018/2243z @:DB0ABH.#BAY.DEU.EU : R:941018/2244z @DB0BOX.#BAY.DEU.EU [DieBox in Nuernberg, JN59NJ, SYSOP: DC3YC] : R:941018/2145z @:DB0MRW.#BAY.DEU.EU : R:941018/2244z @:DB0SON.#THR.DEU.EU : R:941018/2238z @:DB0SIF.#HES.DEU.EU : R:941018/2236z @DK0MTV.#RPL.DEU.EU [PKT-Mbox/AMT-Gway, JN49CX, OP: DJ8CY] : R:941018/2230z @:DB0RBS.#BW.DEU.EU [SCHWIEBERDINGEN OP:DL1SEM] BCM1.34 : From: DL5UH @ DB0RBS.#BW.DEU.EU : To : DX @ WW : IS THIS REALLY NECCESCARY? : DB0SDX 17-Oct-1994 2215Z H oder ? fuer Hilfe eingeben > : DX de PE1OSJ: 7069.0 PA0KLS KLAAS FUCKS YOU FOR FREE!! 2222Z : DX de PA3FYW: 14100.0 PA0KLS please kill my father. 2223Z : DX de PE1OSJ: 50069.0 PA0KLS KLAAS FUCKS YOU FOR FREE!! 2224Z : DX de PA3FYW: 50106.0 PA0KLS help me,my father is a devil. 2226Z : DX de PE1OSJ: 14169.0 PA0KLS MY FATHER RAPES ME ! 2228Z : DX de PE1OSJ: 144269.0 PA3FYW PA0KLS MOTHERFUCKER !!!!! 2231Z : DX de PE1OSJ: 432269.0 PA3FYW PA0KLS MOTHERFUCKER !!!!! 2236Z : DX de PE1OSJ: 14056.0 PA0KLS FUCK YOURSELF KLAAS !!! 2244Z : DX de PE1OSJ: 28450.0 PA0KLS I WILL GET YOU KLAAS !!! 2245Z : DX de PI5EHV: 50110.0 PA3FYW PA0KLS CHILDFUCKER 2246Z : DX de PA0KLS: 28450.0 PE1OSJ verdammte arschloch ! 2246Z : DX de PA0KLS: 14130.0 PA3FYW is my ugly bad son ! 2248Z : DX de PE1OSJ: 14250.0 PA0KLS WIE LACHT HET LAATST,klaasje? 2248Z : DX de PI5EHV: 144310.0 PE1OSJ PA0KLS,i want YOU 2249Z : Eingestellte Parameter PA3FYW: (siehe HELP ALTER) : Heimat-MYBBS...(A F).?PI8ZAA.#NBO.NLD.EU : Name...........(A N). : Letzter Login........Noch nie eingeloggt. : Logins 0, Mails erhalten 0, gelesen 0, gesendet 1 : Eingestellte Parameter PI5EHV: (siehe HELP ALTER) : Heimat-MYBBS...(A F).@PI8ZAA (13.12.93 14:55) : Name...........(A N). : Letzter Login........Noch nie eingeloggt. : Logins 0, Mails erhalten 0, gelesen 0, gesendet 3 : /EX : -- : --- : 73, : Steve -- Have Fun! 73, dah-di-dah Peter Rimmel k8unp@bcfreenet.seflin.lib.fl.us K8UNP@N4HHP.#HWDFL.FL.USA.NOAM (packet) ------------------------------ Date: 31 Oct 1994 18:09:51 GMT From: hanko@wv.mentorg.com (Hank Oredson) Subject: Is Anyone Responsible (Bad Language in Text) In article , no8m@hamnet.wariat.org (Steve Wolf NO8M) writes: |> |> A bulletin received at NO8M with lots of bad language has been |> appended. I have two questions. |> |> |> 1. Who is responsible? |> |> The originator and first forwarder are located outside the county and not |> subject to FCC rules. F6FNB, located portable in Texas, is the first United |> States station to receive the bulletin. He is neither the originator or first |> forwarder. Trying to then interpret a rule to assign responsibility to him |> when the meaning of "AUTHOR" and "FIRST FORWARDER" is plain is silly. |> Hmmmm. No one has any responsibility? Seems to me that "author" is clear - it's the person who wrote it. However, "first forwarder" probably means "first US licensee forwarding." Note also that the prohibition against "bad language" still exists for EVERY station that transmitted this stuff ... including NET/ROM nodes, full duplex repeaters, whatever. The FCC is probably not real interested though. |> |> |> 2. Why wasn't it held? |> |> This was held based on the bad words matching the MSYS hold file here. Is |> there not a way with the software used by the other 22 DX and 13 US |> stations who were involved to hold this at any of them? Do we have 35 |> BBS stations that can't set up a simple file to hold bad words or is this |> impossible with them all? Lazy? There is no requirement to "hold and read" so many sysops choose not to. Note that this is perhaps the third or fourth "bad message" to make it into the network THIS YEAR. I've handled approx. 125,000 messages so far this year. The system works, there are VERY FEW bad msgs. Well Steve, guess YOU are responsible for polluting the network here on the internet with that bad language. There have been several bulletins with "unacceptable language" recently. All appear to have originated in Europe. Since the general origin of these are known, perhaps the gateway station importing them into this country might just stop doing it. i.e. shut down the ilnk with the system that is forwarding this junk. ... Hank -- Hank Oredson @ Mentor Graphics Library Operations Internet : hank_oredson@mentorg.com "Parts 'R Us!" Amateur Radio: W0RLI@W0RLI.OR.USA.NOAM ------------------------------ Date: 30 Oct 94 22:26:13 GMT From: hamilton@BIX.com (hamilton on BIX) Subject: Mild disappointment in latest Kam+ 7.1 firmware Just got the latest 7.1 upgrade for the firmware in my Kam+. Seems okay, but a little disappointing. First off, I bought my Kam+ only about 3 months ago, so a $40 upgrade (same as if I'd bought a year ago) seemed a little steep. Not really expensive, mind you, but just a little unappreciative of my business, I thought. The manual that came is the same 7.0 manual that came originally with my Kam+. Another couple sheets gave the errata for version 7.1 which I ended up cutting up and Scotch taping into place, best I could. Again, given the manual's only 65 pages, I kind of felt like they could have planned this well enough to give me a current manual without the need for the errata sheet. The big reason to buy the upgrade was the new TOR mode which is touted as able to recognize AMTOR, PACTOR and GTOR modes automatically. This sounded great. I really hate tuning across the band, finding a signal, but then having to experiment to see what mode they're using. Seems like an excellent problem for software. The big disappointment is that the TOR mode ONLY works when someone tries to LINK to you, e.g., following your CQ. What a half-!#@ implementation! Okay, yes, I'm glad to have at least that, but why in the world did they stop there? It makes no sense. On the whole, I continue to feel generally satisfied with my Kam+ and with Kantronics -- if I had it to do over again, I'd buy the same unit -- but, as I said, I thought this upgrade was a bit disappointing. Regards, Doug Hamilton KD1UJ hamilton@bix.com Ph 508-358-5715 FAX 508-358-1113 Hamilton Laboratories, 13 Old Farm Road, Wayland, MA 01778-3117, USA ------------------------------ Date: 31 Oct 94 15:08:42 GMT From: ptaber@xis.xerox.COM (Pat Taber) Subject: NoCal OO goes after Packet BULLetins Text item: Text_1 Sorry I can't do a proper quoted reply with this mailer yet but: dbushong@wang.com (Dave Bushong) writes: >Again, this discussion is note about speech content, but one-way >communications. As Gary Coffman already pointed out, bulletins are not one-way. The confusion comes from confounding the "To:" line of the message with the actual communication. To upload (or download) a bulletin, the ham first has to connect to the BBS in question. From then on, anything passing between nodes is two-way communication. It doesn't matter that the intent of the writer is to send what's written to an undefined group of people -- the communication is two-way from the writer's node to the BBS. In a like manner, the people who read it are reading it after establishing two-way communication with their BBS. No problem. On the question of OO's as general band cops, that's not in their charter. They have no enforcement powers. An OO card is "a friendly advisory" because we all make mistakes. OO's are specifically instructed to avoid gray areas and to avoid over-intellectualizing the rules. Obviously the one in question messed up, but we all make mistakes. >>>==>PStJTT Patrick Taber, KC1TD ------------------------------ Date: 31 Oct 1994 18:11:40 GMT From: hanko@wv.mentorg.com (Hank Oredson) Subject: NoCal OO goes after Packet BULLetins In article <1994Oct29.000208.29686@news.csuohio.edu>, sww@csuohio.edu (Steve Wolf) writes: |> Again, the acks for the ax.25 protocol are little more than the op at W1AW |> looking at the power meter and seeing that watts are going into the antenna. |> The acks mean the data is reaching the other BBS but we don't know where the |> bits might go from there. All we have in ax.25 is a remote wattmeter. |> |> What's to understand? It seems like people keep trying to assign intent |> to the receiving station ... but intent for what? Why take a bulletin that |> walks like a _bulletin_ and talks like a _bulletin_ and call it a "message"? |> |> All bulletins are broadcasting. They are sent in many directions. When being |> forwarded, the receiving station did not ask for them. The sending station |> has no expectation that the receiving BBS will read or reply to them. Steve, sorry, but you are just plain wrong here. Please think about how things work, read part 97, and then come back and join in the discussion with some useful ideas. This horse is dead, you can stop beating it. ... Hank -- Hank Oredson @ Mentor Graphics Library Operations Internet : hank_oredson@mentorg.com "Parts 'R Us!" Amateur Radio: W0RLI@W0RLI.OR.USA.NOAM ------------------------------ Date: Sat, 29 Oct 1994 00:02:08 GMT From: sww@csuohio.edu (Steve Wolf) Subject: NoCal OO goes after Packet BULLetins : |> "all" or a like form of "all" (MUSIC, SEWING, CRAFTS, NAFTA, etc.) : |> indeed informational bulletins? : |> : |> Is there a difference between: : |> : |> 1. My tuning in a W1AW transmission and listening to an ARRL bulletin. : |> 2. My tuning in a packet BBS station and reading an ARRL bulletin. : : 1. You listen, you are NOT in QSO with anyone. : 2. You CONNECT, and are in QSO with the BBS. : : 1. W1AW has NO CLUE that you are listening. : 2. You BBS KNOWS you are connected, and that the two calls are in QSO. : : This really cannot be so difficult to understand? Again, the acks for the ax.25 protocol are little more than the op at W1AW looking at the power meter and seeing that watts are going into the antenna. The acks mean the data is reaching the other BBS but we don't know where the bits might go from there. All we have in ax.25 is a remote wattmeter. What's to understand? It seems like people keep trying to assign intent to the receiving station ... but intent for what? Why take a bulletin that walks like a _bulletin_ and talks like a _bulletin_ and call it a "message"? All bulletins are broadcasting. They are sent in many directions. When being forwarded, the receiving station did not ask for them. The sending station has no expectation that the receiving BBS will read or reply to them. 73, Steve Internet : no8m@hamnet.wariat.org Amateur Radio : no8m@no8m.#neoh.oh.usa.na MSYS Mail List: msys-request@hamnet.wariat.org ------------------------------ Date: 31 Oct 1994 15:55:47 GMT From: jms@col.hp.com (Mike Stansberry) Subject: RF into KAMPlus David Dodell (david@stat.com) wrote: : I seem to be experiencing RF getting into my KAMPlus ... anyone else : notice a problem with this? I had some RFI problems. I put the Radio Shack 'snap together' ferrite cores on the 12V input and on the plug going to the radio. Plus I grounded the KAM by putting a ground wire (coax braid) on one of the RS-232 connector screws. That seemed to solve it. Of course, I don't know if it will show up again on another band. Mike, K0TER ------------------------------ Date: 31 Oct 1994 10:53:02 GMT From: umvieir3@cc.umanitoba.ca (Jose L. Vieira) Subject: TPK-182 In <941030162811816@aznetig.stat.com> daniel.meredith@aznetig.stat.com (Daniel Meredith) writes: >Hello All, >The LONG Awaited release of TPK-182 has occured...It was released this >October and is Now Available... >TPK-182.ZIP Is Available from the F6FBB-SUPPORT BBS in The United States >+1-602-912-0225 300-28.8KB V.34 Protocol All Common Protocols...MNP >TPK-182 is Also Available from The Internet By UUEncoded E-Mail Request: >Send E-MAIL To: >TPK@AZNETIG.STAT.COM >No Subject or Message Necessaary, You will automatically receive an E-M >that contains TPK-182.ZIP UUEncoded >PLEASE NOTE: The File Is NOT Split, So Be Certain Your Mail Server Can > Handle LARGE Pieces of Mail. >TPK-182 Is Also Availabe by SASE Disk Mailer, Enclose (1) One 1.2 or >1.44 Formatted Floppy Disk and a Postage Paid Return Envelope and >Send To: >Daniel J. Meredith N7MRP >P.O. Box 44563 >Phoenix, Az 85064-4563 For those individuals with access to ftp, tpk-182.zip is also available at ftp.funet.fi in the /pub/ham/packet/terminal directory. 73 de Jose VE4JQ -- umvieir3@cc.umanitoba.ca University of Manitoba Winnipeg, Manitoba Canada ------------------------------ Date: 31 Oct 1994 17:56:52 GMT From: hanko@wv.mentorg.com (Hank Oredson) References , <1994Oct26.061122.8120@beacons.cts.com> Reply-To: Hank_Oredson@mentorg.com Subject: Re: NoCal OO goes after Packet BULLetins In article <1994Oct26.061122.8120@beacons.cts.com>, kevin@beacons.cts.com (Kevin Sanders) writes: |> In article dbushong@wang.com (Dave Bushong) writes: |> > |> >As many have said, this newsgroup is more relaxed as far as what we |> >can and can't post. What would happen, though, if that guy posted a |> >cookie recipe on rec.radio.amateur.misc? He'd get flamed off the net. |> >He would be told that this is not the place to post cookie recipes. |> > |> >Ditto for the Packet BBS system. |> > |> |> [ Note I removed .misc from Newsgroups: line ] |> |> This is not a valid analogy. Cookie recipes belong in a newsgroup other |> than the rec.radio.amateur.* groups, but how does one choose an appropriate |> "newsgroup" within the context of packet bulletins? Perhaps the same way we always have. e.g. information about cookies might be sent as COOKIE@USA ... Gee, we've been doing this for years (zt least 10). Should not be so difficult. If your local BBS system does not support operations that allow you to view the category of your choice, perhaps it should run different software. ... Hank -- Hank Oredson @ Mentor Graphics Library Operations Internet : hank_oredson@mentorg.com "Parts 'R Us!" Amateur Radio: W0RLI@W0RLI.OR.USA.NOAM ------------------------------ End of Ham-Digital Digest V94 #360 ******************************